The Session Log Window

The Session Log Window allows you to control the recording, playback, and display formatting of MIDI information.  The Session Log Window has six settings buttons on the left side of the window, and a tabular listing of the MIDI messages divided up into four columns covering the majority of the Session Log Window.   The icons associated with different log options and functions will are framed with a dark colored square if they are "on."

The first column indicates the time at which a MIDI event was received by Flypaper.  Times are shown in 

hours : seconds : milliseconds 

format.  The second column shows any recognized cues from the Session's list of cues.  If more than one cue is recognized in the MIDI data, all identified cues will appear in succession in the second column, listed in the order they were identified.  The third column shows the actual MIDI messages.  The fourth column shows which  Flypaper MIDI Manager port the incoming messages were received from.

The scroll bar on the right side of the Session Document's log window is used to scroll through the MIDI messages recorded in the log.  The scroll bar arrows located at the upper and lower extremities of the bar can be used to increment through the log one MIDI byte at a time. 

View Modes: MIDI View and Cue View

Clicking on the MIDI View button will toggle display of MIDI messages in the log on or off.  If you don't want to look at all of the incoming MIDI messages, turn the MIDI View option off.  

Clicking on the Cue View button will toggle display of recognized MIDI cues from your Session's cue definitions on or off.  If you don't want to see which cues are recognized in the list of MIDI messages, turn the Cue View option off.  

Play

Clicking on the Play button will cause the entire Session Log of MIDI to be played out from Flypaper's MIDI Manager outputs.  Input and output connections are assumed to be connected symmetrically in the MIDI Manager Patchbay. For instance, if the MIDI message was originally recorded from Flypaper's Input 1 port, it will be played back through Flypaper's Output 1 port.  If the Autoscroll Log option is on (See Chapter 6- The Options Menu), Flypaper will scroll the log and highlite the current playback entry as it plays the log back.

Stop

Clicking on the Stop button will cause playback of the MIDI log to cease.  The Stop button only works when a Flypaper log is being played back.

Record

Clicking on the Record button will trigger one of three recording modes for MIDI messages.  The first mode is indicated by a flashing red or black border around the Record button, called trigger record.  In trigger record, Flypaper waits until MIDI messages come in, and then begins recording the MIDI messages into the log.  The first MIDI message received is considered to be at time 0:00:00.  The second recording mode is called record start and is indicated by a solid red or black border around the Record button.  In record start mode, Flypaper immediately begins recording any MIDI messages.  The first piece of MIDI information is considered to be at time relative to when record start mode was initiated.  The final recording mode, record mute is indicated by two black slash lines through the Record button in addition to a black border around the Record button.  In record mute mode, no MIDI messages will be recorded to the log.

Stopping Hung Notes, All Notes Off

If you have notes that are stuck on your synthesizer, you can issue an "All Notes Off" command to all MIDI ports and channels attached to Flypaper by selecting the "Reset/All Notes Off" item from the Options menu.  This feature is also useful to bring all Session Definitions up to date with MIDI that has been stored on disk.  For instance, if Flypaper falls far behind in identifying cues, you can "catch up" with the "Reset/All Notes Off" menu selection.

Creating Transportable Updater Applications

Flypaper can place the MIDI data from your Session Log into a transportable application that other users can use to receive sequences, system exclusive patches, or any other MIDI data that you have recorded.   You are free to distribute Transportable Update applications created by Flypaper with no licensing fees or other costs as long as you do not modify the original Transportable Updater application.  
 
In order to use the Transportable Updater option, you must first create a copy of the "Transportable Updater.Original" file that came with your Flypaper application.  You can do this from the Finder by finding and selecting the "Transportable Updater.Original" application and then selecting "Duplicate" from the File menu in the Finder.  Never create an updater from your original "Transportable Updater.Original" file, as you will not have a "blank" to install the MIDI messages into any longer.  If this happens, reinstall the "Transportable Updater.Original" application from your Flypaper installation disks.

The Transportable Updater contains a compressed copy of your Session Log's MIDI messages and allows for the playback of the messages to another user's MIDI devices through a simple interface. 

After recording MIDI messages into a Session Document's log, use the "Create Updater" command from the File menu.  Updaters contain a "comments" field that you may enter with up to 255 characters describing the contents of the Transportable Updater.  You will be asked to enter the comment after you choose the "Create Updater" item from the File menu.

After entering the comments for your Transportable Updater, the Standard File Picker will appear, asking you to locate a COPY of the Transportable Updater application that came with your Flypaper installation.  Find the duplicate of the Transportable Updater application and click "Open".  Flypaper will automatically install the contents of your current Session Document's log into the Transportable Updater.